Skip to content

BUG/CLN: use more-correct isinstance check #31180

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jan 24, 2020

Conversation

jbrockmendel
Copy link
Member

this is only kind of a bug, since the isinstance check still returns True on the type(obj)

@WillAyd
Copy link
Member

WillAyd commented Jan 21, 2020

Makes sense

this is only kind of a bug, since the isinstance check still returns True on the type(obj)

So are there any code paths you could see hitting this?

@jbrockmendel
Copy link
Member Author

jbrockmendel commented Jan 21, 2020 via email

@jreback jreback added the Dtype Conversions Unexpected or buggy dtype conversions label Jan 24, 2020
@jreback jreback added this to the 1.1 milestone Jan 24, 2020
@jreback
Copy link
Contributor

jreback commented Jan 24, 2020

does this any tests?

@jbrockmendel
Copy link
Member Author

does this any tests?

no, it doesnt actually change any behavior

@jreback jreback merged commit c02302d into pandas-dev:master Jan 24, 2020
@jbrockmendel jbrockmendel deleted the bug-numeric-is_compat branch January 24, 2020 04:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dtype Conversions Unexpected or buggy dtype conversions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants